SSW Update - Are your settings and the customizable settings, in different files?

Tech Breakfast

1. Upgrade your Access 97 database to Access 2003
2. Upsize your Access 2003 database to SQL Server 2000
3. Recreate your Access reports using the new Reporting Services
4. Recreate your Access forms using .NET Windows Forms

This session is a must for all Access developers! Prerequisites: You should have a working knowledge of Access, including using forms, basic VBA code, and designing simple reports. Register online now or call (02) 9953 3000

ASP.NET Whidbey is the current name for the next version of ASP.NET. Adam Cogan will give a talk on: ASP.NET Whidbey overview, working with data, caching improvements to significantly boost the performance of the next generation of ASP.NET applications, master pages for consistent web sites, new membership features, and personalization.
Prerequisites: To get the most out of this session, attendees should be familiar with ASP.NET.

Resources

Tips

The Cutting Edge

Are your settings and the customizable settings, in different files?

There are three types of settings files that we may need to use in .NET

1. App.Config/Web.Config is the default .NET settings file, including any settings for the Microsoft Application Blocks (eg. the Exception Management Block and the Configuration Management Block). These are for settings that dont change from within the application. In addition, System.Configuration classes dont allow writing to this file.

2. ToolsOptions.Config (an SSW standard) is the file to hold the users own settings, that are users can change in the Tools - Options. Eg. ConnectionString, EmailTo, EmailCC Note: We read and write to this using Microsoft Configuration Application Block. If we dont use this Block we would store it as a plain XML file and read and write to it using System.XML classes. The idea is that if something does go wrong when you are writing to this file, at least the App.Config would not be affected. Also, this separates our settings (which are few) from the App.Config (which usually has a lot of stuff that we really dont want a user to stuff around with).

3. UserSession.Config (an SSW standard). These are for additional setting files that the user cannot change. e.g. FormLocation, LastReportSelected Note: This file is over writable (say during a re-installation) and it will not affect the user if the file is deleted.

Cheers until next time, Adam
SSW Chief Architect and Microsoft Regional Director, Australia

Got a comment for Adam? Email Adam

Sydney .NET User Group - The best place to learn .NET for free in Sydney

Come along this week and let Adam guide you through ADO.NET 2.0. You'll get a close-up of:

• DataBinding
• (the vastly improved) DataGrid
• Input Validation

Mehmet Ozdemir will provide a quick walk through on the Visual Studio 2005 Web Testing components. He will demonstrate alternative uses for web testing and how to interrogate the resultant log files, including running through some code samples.

We have lots of hot giveaways this week, including copies of Visual Studio .NET 2005 Beta 2. Not to mention the free Pizza & soft drinks!

SSW Upsizing PRO! - Migrate from Access to SQL with minimal fuss

Our clients often ask us to upsize their database from Access to SQL Server. With Upsizing PRO!, what used to take us hours can now be done at the click of a button. SSW Upsizing PRO!.

Take a look at what Russell Sinclair, SQL Server Professional had to say about SSW Upsizing PRO!

SSW Employment Opportunities